CA-TSS security administrator must develop a process to suspend userids found inactive for more than 35 days.

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

CA-TSS security administrator must develop a process to suspend userids found inactive for more than 35 days.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-223953	TSS0-ES-000800	SV-223953r561402_rule		Medium

Description
Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.

STIG	Date
IBM z/OS TSS Security Technical Implementation Guide	2022-09-19

Details

Check Text ( C-25626r516258_chk )
From the ISPF Command Shell enter: TSS LIST(ACIDS) If every user shows a LAST-USED=yy.ddd within the past "35" days, this is not a finding. NOTE: VALID FOR INTERACTIVE USERIDS, NOT VALID FOR STARTED TASK USERIDS AND BATCH USERIDS.

Fix Text (F-25614r516259_fix)
Develop a procedure to check all userids for inactivity of more than "35" days. If found, the ISSO must suspend an account, but not delete it until it is verified by the local ISSO that the user no longer requires access. If verification is not received within "60" days, the account may be deleted.